Add bootstrap-migrate-v3-to-v5 skill for Power Pages (Bootstrap 3 -> 5) - #181

plugins/power-pages/skills/bootstrap-migrate-v3-to-v5/SKILL.md:9

• PR title/description says this adds a /power-pages:migrate-to-v5 skill, but the implementation and documentation added in this PR are consistently named /bootstrap-migrate-v3-to-v5 (skill frontmatter name, README section, evals, approval-gates, tracking mapping). Please align the PR metadata and/or the skill naming so users know the correct invocation name.

name: bootstrap-migrate-v3-to-v5
description: >-
  Migrates a traditional Power Pages site from Bootstrap 3 to Bootstrap 5. Downloads the
  site, runs the pac pages bootstrap-migrate engine, reviews the change report, applies
  AI-assisted fixes for the residual hierarchy/CSS changes the engine only flags, uploads
  the migrated site (which auto-enables the Bootstrap 5 runtime flag), verifies the flag,
  and validates. Use when the user wants to upgrade an older Bootstrap-3 portal to
  Bootstrap 5. NOT for code sites (React/Vue/Angular/Astro) — those are never Bootstrap-3.

plugins/power-pages/skills/bootstrap-migrate-v3-to-v5/SKILL.md:3

• The PR description/title mention a /power-pages:migrate-to-v5 skill, but the implemented skill name is bootstrap-migrate-v3-to-v5 (and docs/evals also use that). This mismatch will confuse users and makes it unclear which invocation name is intended. Align the PR description and/or rename the skill (including folder name, references, approval-gates entry, README section, and evals) so there is a single canonical command name.

---
name: bootstrap-migrate-v3-to-v5
description: >-

plugins/power-pages/skills/bootstrap-migrate-v3-to-v5/SKILL.md:383

• This step says --projectRoot "<MIGRATED_FOLDER>" is "the folder containing powerpages.config.json", but this skill explicitly targets classic/traditional downloads where powerpages.config.json is not present. The parenthetical is misleading and contradicts the next sentence that says tracking is a no-op for traditional sites.

3. **Record skill usage** — follow `${PLUGIN_ROOT}/references/skill-tracking-reference.md`, passing
   `--projectRoot "<MIGRATED_FOLDER>"` (the folder containing `powerpages.config.json`) and
   `--skillName "BootstrapMigrateV3ToV5"`. Tracking only writes when the project is a **code site**
   (`.powerpages-site/site-settings/` exists); for a traditional/native download the script exits
   silently as a no-op — that is expected, so call it unconditionally and don't treat the no-op as an
   error. If tracking files are written, include them in the final commit.

plugins/power-pages/skills/bootstrap-migrate-v3-to-v5/SKILL.md:110

• Phase 2’s local-folder validation currently checks for website.yml and sitesetting.yml at the root. In this plugin, PAC-downloaded site identity is normally .powerpages-site/website.yml and site settings live under .powerpages-site/site-settings/ (see scripts/lib/detect-project-context.js:72-105). As written, a valid downloaded site can be incorrectly rejected.

- **If the user provided a local site folder path** (or `$ARGUMENTS` names one): verify it exists
  and looks like a downloaded traditional site (contains `website.yml` and `sitesetting.yml`). Use it
  as `SITE_FOLDER`.

plugins/power-pages/skills/bootstrap-migrate-v3-to-v5/SKILL.md:313

• The Phase 7.1 pre-flight checks reference website.yml containing adx_websiteid and a monolithic sitesetting.yml. In this repo, .powerpages-site/website.yml is a flat file with id: / name: keys (scripts/lib/detect-project-context.js:72-105), and site settings are stored as separate *.sitesetting.yml files under .powerpages-site/site-settings/. Please align the gating checks to that structure (or explicitly call out if this migration engine uses a different legacy layout).

- `website.yml` must have a valid `adx_websiteid`.
- `sitesetting.yml` must contain `Site/BootstrapV5Enabled` with value `true`.

Verify both (`Grep`/`Read`). If either is missing, the flag flip silently no-ops — fix before uploading.

plugins/power-pages/skills/bootstrap-migrate-v3-to-v5/SKILL.md:382

• The skill-usage tracking guidance is internally inconsistent: it says --projectRoot "<MIGRATED_FOLDER>" is “the folder containing powerpages.config.json”, but this skill is explicitly for traditional/non-code sites (which typically do not have powerpages.config.json). Also, the tracking script requires --authoringTool (plugins/power-pages/references/skill-tracking-reference.md, plugins/power-pages/scripts/update-skill-tracking.js:29-32).

3. **Record skill usage** — follow `${PLUGIN_ROOT}/references/skill-tracking-reference.md`, passing
   `--projectRoot "<MIGRATED_FOLDER>"` (the folder containing `powerpages.config.json`) and
   `--skillName "BootstrapMigrateV3ToV5"`. Tracking only writes when the project is a **code site**
   (`.powerpages-site/site-settings/` exists); for a traditional/native download the script exits
   silently as a no-op — that is expected, so call it unconditionally and don't treat the no-op as an

plugins/power-pages/skills/bootstrap-migrate-v3-to-v5/references/migration-engine-reference.md:41

• This step claims the engine appends Site/BootstrapV5Enabled into a monolithic sitesetting.yml. Elsewhere in the plugin, site settings are represented as individual *.sitesetting.yml files under .powerpages-site/site-settings/ (see plugins/power-pages/scripts/create-site-setting.js and references/skill-tracking-reference.md). Consider rewording this to describe the setting by name/value rather than a single-file format.

3. Replaces the embedded `bootstrap.min.css` (v3) with the Bootstrap 5 stylesheet.
4. Appends a `Site/BootstrapV5Enabled` record (value `true`) to `sitesetting.yml`
   (skipped if already present).

plugins/power-pages/skills/migrate-bootstrap/SKILL.md:2

• PR title/description says this adds /power-pages:bootstrap-migrate-v3-to-v5, but the shipped skill is named migrate-bootstrap (and README/evals/approval-gates also reference /migrate-bootstrap). Please align the PR metadata and the skill invocation name so users aren’t told to run a command that doesn’t exist, or rename the skill + all references consistently.

name: migrate-bootstrap

plugins/power-pages/skills/migrate-bootstrap/SKILL.md:383

• --projectRoot "<MIGRATED_FOLDER>" (the folder containing powerpages.config.json) is misleading for classic/traditional downloads (they don’t have powerpages.config.json). Suggest wording that --projectRoot should be the code-site root when applicable, and that passing <MIGRATED_FOLDER> for classic sites is fine because the script no-ops unless .powerpages-site/site-settings/ exists.

   `--projectRoot "<MIGRATED_FOLDER>"` (the folder containing `powerpages.config.json`) and